Skip already-contained integration sources#40
Closed
mberman84 wants to merge 1 commit into
Closed
Conversation
4ce3009 to
4c44798
Compare
Contributor
Author
|
Superseded by #45, which includes the contained-source/no-op merge recovery together with the dispatch, multi-workflow release-state, and status-path fixes from the broader deploy audit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
GitHub returned invalid JSONconflicts.Last-hour incident
Astro integration PR #922 had already merged cumulative PR #916, which contained #912 and #907. DeployBot retried #912, received GitHub's empty no-op response, and created an unnecessary repair handoff.
Composition with v0.2.16
Rebased onto the failed-integration intent-preservation release at
860b5e5257a802faa8a39d34a354484b106e13c3. The combined controller passes all gates.Validation